-
Notifications
You must be signed in to change notification settings - Fork 32
♻️Maintenance: fix generation of service names #8377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
♻️Maintenance: fix generation of service names #8377
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
A maintenance refactor that fixes service name generation by replacing the word-based suffix with a more controlled string generation approach.
- Changed suffix generation from
fake.unique.word()tofake.unique.pystr(min_chars=2)to ensure consistent service name format
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8377 +/- ##
=======================================
Coverage 87.90% 87.91%
=======================================
Files 1951 1951
Lines 75927 75927
Branches 1337 1337
=======================================
+ Hits 66745 66750 +5
+ Misses 8783 8778 -5
Partials 399 399
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
@mergify queue |
🛑 Configuration not compatible with a branch protection settingThe branch protection setting |
pcrespov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx



What do these changes do?
sometimes the faker generate words like
awhich cannot be used safely as docker service names...Related issue/s
How to test
Dev-ops